Repository navigation
Use the SDK's one destructive declaration and guard; drop MICROSOFT_ALLOW_DESTRUCTIVE (requires scion-sdk 0.10.2) - #39
Merged
Conversation
Destructive Microsoft operations had their own gate: a MICROSOFT_ALLOW_DESTRUCTIVE setting checked by the tool policy and the Windows companion tool, and a destructive_action_acknowledged field in the Intune confirmation evidence. That gate is removed. Eleven Graph client methods the SDK would not classify (application passwords, service principals, role assignments, conditional access, organization and admin SharePoint updates, risky-user dismissal, device wipe and retire) carry the SDK declaration, and the hand-written destructive tools (Intune reboot and shutdown, desktop-flow cancellation, PowerPoint slide deletion, Windows companion actions) run the SDK guard. Each served tool has the MCP destructive hint and the standard confirm argument; a call without a live confirmation makes no request. MICROSOFT_ALLOW_WRITES stays as deployment access scope. The single operator setting for unattended use is SCION_ALLOW_DESTRUCTIVE. Requires scion-sdk 0.10.2. Impact: MICROSOFT_ALLOW_DESTRUCTIVE is no longer read; callers pass confirm (or are confirmed by the gateway); Intune evidence no longer carries an acknowledgement field. Verification: 52 targeted tests pass, including a served check of the hint and confirm argument on every destructive tool and a refusal check that sends no request. Spec: CONN-MICROSOFT-AGENT-CONNECTOR-CONTENT-R002 (destructive operations use the SDK declaration and guard) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Knucklessg1
force-pushed
the
feat/microsoft-standard-destructive
branch
from
November 12, 2026 19:53
53694da to
db29a6b
Compare
Message and Event now extend core DomainEntity and File extends core Artifact so the connector-surface ontology check passes. Spec: none (class roll-up to the core ontology; no new requirement) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Member
Author
Pre-merge test run: PASSEDWhat this is: the full test and lint suite of this repository, run before merge on the tested tree below, because the hosted checks are not the gate for this change. Impact: the change is cleared to merge. Tested tree: the pull request head
Total time 2m19s. Verification: each check above was run on the tested tree and the result is the exit status of the repository's own commands. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Destructive operations are declared with the SDK and decided by its guard. The
MICROSOFT_ALLOW_DESTRUCTIVEsetting and thedestructive_action_acknowledgedfield of the Intune confirmation evidence are removed. Eleven Graph client methods the SDK would not classify carrydestructive_operation; the Intune reboot and shutdown, desktop-flow cancellation, PowerPoint slide deletion and destructive Windows companion actions runguard_destructive. Each served tool has the MCP destructive hint and the standardconfirmargument.MICROSOFT_ALLOW_WRITESstays as deployment access scope.Why
An agent must not be able to self-authorize a destructive call: the gateway asks a human to approve a call classified by the hint, clients that cannot be asked pass
confirm, and unattended operation uses the single operator settingSCION_ALLOW_DESTRUCTIVE.Impact
MICROSOFT_ALLOW_DESTRUCTIVEis no longer read; callers passconfirmor are confirmed by the gateway. Requires scion-sdk 0.10.2.Verification
52 targeted tests pass, including a served check that every destructive tool has the hint and a
confirmargument and no allow argument, and a refusal check that sends no request.Spec: CONN-MICROSOFT-AGENT-CONNECTOR-CONTENT-R002 (destructive operations use the SDK declaration and guard)
🤖 Generated with Claude Code